Repository navigation
ci: publish prereleases to named npm channels - #491
Merged
Merged
Conversation
The Release workflow accepted only stable versions, so a branch like the Nitro V1 lane could not publish a preview. Exact prerelease versions such as 11.0.0-nitro-v1.0 now publish to an npm channel named after their prerelease identifiers, never move latest, and mark the GitHub release as a prerelease. A new prerelease increment continues a channel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Release Please's JSON updater stops matching a prerelease at the first hyphen, so bumping 11.0.0-nitro-v1.0 wrote 11.0.0-nitro-v1.1-v1.0 into the package manifests. The patch lets prerelease identifiers contain hyphens, as semantic versioning allows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Release workflow only accepts stable versions, so we can't publish a preview from a branch like the Nitro V1 lane. This PR lets the workflow take an exact prerelease version and publish it to an npm channel named after the prerelease, without touching
latest.For example, running the workflow on a branch with version
11.0.0-nitro-v1.0publishes both packages under thenitro-v1dist-tag, so users install them withreact-native-nitro-sqlite@nitro-v1. The GitHub release is marked as a prerelease. Later runs on that branch can passprereleaseto publish11.0.0-nitro-v1.1, andpatch,minor, ormajorfrom a prerelease finishes that version (11.0.0-nitro-v1.3becomes11.0.0). Stable releases and the maintenance channels work as before. The release docs describe the new channels.A branch needs these release scripts before it can publish a prerelease, the same as maintenance branches.
🤖 Generated with Claude Code